Splice Signalling Buffer Characteristics

ABSTRACT

In one method embodiments, providing a transport stream to a client device, the transport stream comprising a head stream and a tail stream, the head stream and the tail stream each comprising a compressed video sequence; providing information in a transport stream packet associated with the head stream, the information configured to cause the client device to selectively control an output of at least one of a plurality of pictures of the head stream yet to be output from a decoded picture buffer (DPB) at an out-point from the head stream to the trail stream.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No. 12/779,035, filed May 12, 2010, which claims priority to and the benefit of U.S. Provisional Patent Application No. 61/177,336, filed on May 12, 2009, now expired, both of which are entirely incorporated herein by reference.

TECHNICAL FIELD

This disclosure relates in general to television systems, and more particularly, to video processing in television systems.

DESCRIPTION OF THE RELATED ART

Broadcast and on-demand delivery of digital audiovisual content has become increasingly popular in cable and satellite television networks (generally, subscriber television networks). Various specifications and standards have been developed for communication of audiovisual content, including the MPEG-2 video coding standard and AVC video coding standard. One feature pertaining to the provision of programming in subscriber television systems requires the ability to concatenate video segments or video sequences, for example, as when inserting television commercials or advertisements. For instance, for local advertisements to be provided in national content, such as ABC news, etc., such programming may be received at a headend (e.g., via a satellite feed), with locations in the programming allocated for insertion at the headend (e.g., headend encoder) of local advertisements.

BRIEF DESCRIPTION OF THE DRAWINGS

The systems and methods described herein can be better understood with reference to the following drawings. The components in the drawings are not necessarily drawn to scale, emphasis instead being placed upon clearly illustrating the principles of the present disclosure. In the drawings, like reference numerals designate corresponding parts throughout the several views.

FIG. 1 is a block diagram that illustrates an example environment for implementing assistive information systems.

FIG. 2 is a block diagram of an example embodiment of a digital home communications terminal (DHCT).

FIGS. 3A-3B are block diagrams that illustrates an example embodiment of splicing mechanisms pertaining to yet to be output picture (YTBOP) intervals.

FIG. 4 is a flow diagram that illustrates an example headend side method for providing splice-out point properties.

FIG. 5 is a flow diagram that illustrates an example splicer method for receiving and processing splice-out point properties.

DESCRIPTION OF EXAMPLE EMBODIMENTS

Overview

In one method embodiments, providing a transport stream to a splicing device, the transport stream comprising a head stream concatenated to a tail stream, the head stream and the tail stream each comprising a compressed video sequence from a separate video source; providing in an adaptation field of a transport stream packet corresponding to the head stream an out-point that corresponds to a provided splice point, the splice point provided based on presentation time stamp (PTS) value, the out-point signaled by a descriptor in a program map table (PMT), the transport packet further comprising assistive information comprising one or more compressed picture buffer properties and one or more decoded picture buffer properties that are used in the concatenation of the head stream and the tail stream.

Example Embodiments

Certain assistive information (AI) system and method embodiments are disclosed that incorporate logic to provide, receive, and/or process information (e.g., messaging) in a video stream that signals to a digital home communications terminal (DHCT) a manner of managing, processing, and/or outputting buffered pictures. In one embodiment, a splice point (cut) in the video stream that corresponds to a provided splice point, announced as a presentation time stamp (PTS), is provided in an adaptation field of a transport packet. The provision of a splice point using the PTS is via SCTE-35 cue messaging, which is the current mechanism employed in MPEG-2 video. However, with AVC/H.264, finding the exact point in the video stream (e.g., in decode or transmission order) that corresponds to such a cue that signals the splice point in the video stream with a presentation time stamp (PTS) value is difficult. In one embodiment, the AI system signals the corresponding splice point (cut) in decode order so that it may be explicitly corresponded with existing mechanisms in use today for programs that have the video encoded according to MPEG-2 video. In addition, a program map table (PMT) is used to announce that the cut exists and that it is being provided in the transport packet. The corresponding cut is provided immediately prior to the cut point in decode order.

In some embodiments of the AI system, assistive information comprising properties of a decoded picture buffer (DPB) and/or a compressed picture buffer (CPB) is provided. For instance, with regard to CPB properties, since the CPB is much larger that MPEG-2 video's bit buffer, the large headroom results in error effects that accrue until carried ailments surface. Such error effects may result from buffer underrun/overruns over multiple splice operations that may provide a compounded effect. One mechanism to address such errors is to provide, at the out-point (splice-out point), assistive information corresponding to one or more CPB properties, such as the time of buffering (DTS-STC), the buffer level, the AVC level (e.g., L3.0, L4.0, L4.2), and upper and lower bounds for the intended levels of the CPB.

In some embodiments, the in-point (splice-in point) also needs consideration. For instance, and as explained further below in association with FIGS. 3A-3B, the time or interval corresponding to the yet to be output pictures (YTBOPs) in the head stream at the out-point should be honored. For instance, when the issuance of a no_output_of_prior_pics_flag forces the decoder to disregard the output of DPB pictures (e.g., because of non-contiguous output times), the output of blank pictures may be required to maintain consistent CPB levels. With gaps in output time (e.g., non-contiguous PTS) of pictures in the DPB yet to be output at the splice point, a compliant AVC decoder is challenged—the no_output_of_prior_pics_flag is set equal to one (1) to prevent the output of those YTBOP pictures in the DPB. If the output of these decoded pictures is skipped (e.g., not displayed), a splicing device needs to improvise to for a number of output intervals equal to the number of DPB pictures that are not output (e.g., per a YTBOP flag) while accumulating pictures into the CPB to raise buffer levels (e.g., to avoid buffer underflow). With multiple splice operations, as noted above, the skipping of decoded pictures raises the risk of buffer underflow. If the latest PTS among the pictures yet to be output in the DPB at the splice point is signaled (e.g., last_PTS_flag), then a splicing device, without having to decode and determine based on the decoding operation, knows to provide that many pictures (delay their output) to compensate for the non-output, decoded pictures. While filling the CPB, a receiver either has to blank out pictures (e.g., black pictures) or continuously repeat the last output picture prior to the splice point. One mechanism to achieve this function is by the splicing device signaling the last output picture to be repeated. Further, byte stuffing in blank pictures may raise the CPB buffer level. Accordingly, the assistive information pertaining to the DPB properties includes one or more of configuring of the YTBOP of the head stream (at the out-point) with a maximum of sixteen 16 (e.g., four (4) bits), and a YTBOP_flag that provides all YTBOP pictures in the DPB have successive picture-output times and the first output time of the YTBOP pictures is the first frame interval after the out-point.

In some embodiments, the assistive information is not provided if it is not desired to output pictures from the DPB that would otherwise be discarded. Assistive information that specifies the output behavior of each non-previously output DPB picture allows for outputting a picture, not outputting, or outputting the picture for a number consecutive times prior to outputting the subsequent picture, as is explained further below.

In one embodiment, the assistive information is provided by a splicing device to a DHCT to convey information that alleviates the non-seamless transition incurred by repeating, over multiple frame times, the last output picture from a head stream at a splice operation. As a picture from the head stream is output from the DPB during a transition period from the head stream to a tail stream, control information specifies the outputting of each YTBOP from the DPB of the head stream.

Outputting may be consistent with a pic_struct, but for interlaced sources, a splicing device should provide information to prohibit the manifestation of motion jitter. Hence, for interlaced sources, the last output field of an interlaced frame is output, as both the top and bottom fields, to satisfy the repetition amount specified by command in the message.

The below description is provided in the context of a subscriber television system (STS) using a splicing device (also referred to herein as a splicer) and a DHCT that sends and receives, respectively, the messaging, with the understanding that other devices are contemplated to be within the scope of the disclosure. Additionally, the terms “frames” and “pictures” are used interchangeably herein unless specifically distinguished for purposes of explanation. Further, the discussion below is applicable to AVC access units in place of pictures. The description below also contemplates knowledge, by those having ordinary skill in the art, of MPEG-2 and AVC video coding and associated transport mechanisms, the known references or publications of which are as follows: a description of the MPEG-2 Video Coding standard can be found in the following publication: (1) ISO/IEC 13818-2, (2000), “Information Technology—Generic coding of moving pictures and associated audio—Video;” a description of the AVC video coding standard can be found in the following publication: (2) ITU-T Rec. H.264 (2005), “Advanced video coding for generic audiovisual services;” a description of MPEG-2 Systems for transporting AVC video streams in MPEG-2 Transport packets can be found in the following publications: (3) ISO/IEC 13818-1, (2000), “Information Technology—Generic coding of moving pictures and associated audio—Part 1: Systems,” and (4) ITU-T Rec. H.222.0|ISO/IEC 13818-1:2000/AMD.3, (2004), “Transport of AVC video data over ITU-T Rec. H222.0|ISO/IEC 13818-1 streams.”

FIG. 1 is a high-level block diagram depicting an example environment in which one or more embodiments of assistive information (AI) systems are implemented. In particular, FIG. 1 is a block diagram that depicts an example subscriber television system (STS) 100. In this example, the STS 100 includes a headend 110 and one or more digital home communications terminals (DHCTs) 200. The DHCTs 200 and the headend 110 are coupled via a network 130. The headend 110 and the DHCTs 200 cooperate to provide a user with television services, including, for example, broadcast television programming, interactive program guide (IPG) services, video-on-demand (VOD), and pay-per-view, as well as other digital services such as music, Internet access, commerce (e.g., home-shopping), voice-over-IP (VOIP), and/or other telephone or data services.

The STS 100 may comprise an IPTV network, a cable television network, a satellite television network, or a combination of two or more of these networks or other networks. Further, network PVR and switched digital video are also considered within the scope of the disclosure. Although described in the context of video processing, it should be understood that certain embodiments of the AI systems described herein also include functionality for the processing of other media content such as compressed audio streams.

The headend 110 may include one or more server devices (not shown) for providing video, audio, and other types of media or data to client devices such as, for example, the DHCT 200. The headend 110 may receive content from sources external to the headend 110 or STS 100 via a wired and/or wireless connection (e.g., satellite or terrestrial network), such as from content providers, and in some embodiments, may receive package-selected national or regional content with local programming (e.g., including local advertising) for delivery to subscribers. The headend 110 also receives splice triggers indicative of suitable splice points in the network feed. The headend 110 also includes one or more encoders (encoding devices or compression engines) 111 (one shown) and one or more video processing devices embodied as one or more splicers 112 (one shown) coupled to the encoder 111. In some embodiments, the encoder 111 and splicer 112 may be co-located in the same device and/or in the same locale (e.g., both in the headend 110 or elsewhere), while in some embodiments, the encoder 111 and splicer 112 may be distributed among different locations within the STS 100. For instance, though shown residing at the headend 110, the encoder 111 and/or splicer 112 may reside in some embodiments at other locations such as a hub or node. The encoder 111 and splicer 112 are coupled with suitable signalling or provisioned to respond to signalling for portions of a video service where commercials are to be inserted. For instance, the encoder 111 may receive splice triggers and provide messaging that announces to the splicer 112 suitable splice points corresponding to the splice triggers.

The AI systems and methods disclosed herein are applicable to any video compression method performed according to a video compression specification allowing for at least one type of compressed picture that can depend on the corresponding decompressed version of each of more than one reference picture for its decompression and reconstruction. For example, the encoder 111 may compress an inputted video signal (e.g., provided by a service provider in one of any of several forms, image capture device, a headend server, etc.) according to the specification of the AVC standard and produce an AVC stream containing different types of compressed pictures with a common picture format, some that may have a first compressed portion that depends on a first reference picture for their decompression and reconstruction, and a second compressed portion of the same picture that depends on a second and different reference picture. Since the compressed video (and audio) streams are produced in accordance with the syntax and semantics of a designated video (and audio) coding method, for example AVC, the compressed video (and audio) streams can be interpreted by an AVC-compliant decoder for decompression and reconstruction at the time of reception, at a future time, or both.

In one embodiment, each AVC stream is packetized into transport packets according to the syntax and semantics of transport specification, such as, for example, MPEG-2 transport defined in MPEG-2 systems. Each transport packet contains a header with a unique packet identification code, or PID, associated with the respective AVC stream. In one implementation, the encoded audio-video (A/V) content for a single program may be the only program carried in a transport stream (e.g., one or more packetized elementary stream (PES) packet streams sharing a common time base for the same video service), and in other implementations, the encoded A/V content for multiple programs may be carried as multiplexed programs in an MPEG-2 transport stream, each program associated with its own respective time base.

The header of a transport stream may include a sync byte that sets the start of a transport stream packet and allows transmission synchronization. The header of the transport stream may further include a payload unit start indicator that, when set to a certain value in the packets carrying the video stream, indicates that the transport packet's payload begins with a first byte of a packetized elementary stream (PES). Video streams carried in a PES may be constrained to carrying one compressed picture per PES packet, and to a requirement that a PES packet must always commence as the first byte of a transport streams' packet payload. Thus, the payload unit start indicator provisions the identification of the start of each successive picture of the video stream carried in the transport stream. Note that the transport packets carrying the video stream are identified by the parsing capabilities of DHCT 200 or other network devices from program associated information or program specific information (PSI). For instance, in MPEG-2 Transport, program map tables identify the packet identifier (PID) of the video stream in the program map table (PMT), which in turn is identified via the program association table (PAT).

In IPTV implementations, the program or transport stream may be further encapsulated in Internet protocol (IP) packets, and delivered via multicast (e.g., according to protocols based on Internet Group Management Protocol (IGMP), among other protocols), or in other cases such as video-on-demand (VOD), via unicast (e.g., Real-time Streaming Protocol or RTSP, among other protocols). For instance, multicast may be used to provide multiple user programs destined for many different subscribers. Communication of IP packets between the headend 110 and the DHCTs 200 may be implemented according to one or more of a plurality of different protocols or communication mechanisms, such as User Datagram Protocol (UDP)/IP, Transmission Control Protocol (TCP)/IP, transport packets encapsulated directly within UDP or Real-time Transport Protocol (RTP) packets, among others.

The encoder 111 provides a compressed video stream (e.g., in a transport stream) to the splicer 112 while both receive signals or cues that pertain to splicing or digital program insertion at the transport level. In some embodiments, the splicer 112 and/or DHCT 200 may receive information at other levels (e.g., non-transport levels, such as video coding levels), in lieu of or in addition to the transport stream information. In some embodiments, the encoder 111 does not receive these signals or cues.

In one embodiment of an AI system, the encoder 111 provides the assistive information corresponding to a splice point. As explained previously, the presence in a transport packet of the splice point that corresponds to the splice point corresponding to a PTS (e.g., as communicated via SCTE-35 messaging) may be announced to the splicer 112 via an SCTE adaptation field data descriptor in an elementary stream (ES) loop (e.g., ES_info_loop) of a program specific information table, such as a program map table (PMT). In one embodiment, the splice point is signaled immediately prior to the out-point in decode order, or in some embodiments, N pictures ahead.

The transport packet announced in advance via the SCTE adaptation field data descriptor in the ES_info_loop carries the assistive information in the adaptation field, such as in the private data bytes of the adaptation field. The assistive information may be provided, in embodiment, by a construct such as:

[TAG] [LENGTH] [DATA]

In one embodiment, a specific TAG value is assigned to this particular type of assistive information, and the data carries the assistive information described herein (e.g., DPB properties, the manner of output of YTBOP residing in the same, and/or compressed picture buffer (CPB) properties, such as DTS-STC, buffer level (e.g., top and/or bottom bounds), AVC level (e.g., L3.0, L4.0, L4.2, using, for instance, two bits), among other properties). The provision of the announcement and assistive information in the transport layer avoids the need to parse all the encapsulating layers to find information in the video stream.

In some embodiments, the assistive information and the announcement (e.g., announcing the splice point or packet just prior to the splice point corresponding to where the assistive information is to become effective) are combined in a single packet, and in some embodiments, the announcement and/or the assistive information is not provided (e.g., is optionally provided or functionality conforming to the information is implied).

The splicer 112 splices one or more video streams (e.g., tail streams, such as provided by a video source separate from the video source that provides the first video stream) into designated portions of the video stream (e.g., head stream) provided by the encoder 111 according to one or more suitable splice points, and/or in some embodiments, replaces one or more of the video sequences provided by the encoder 111 with other video sequences. Further, the splicer 112 may pass the assistive information provided by the encoder 111, with or without modification, to the DHCT 200, or the encoder 111 may provide the information directly (bypassing the splicer 112) to the DHCT 200.

Having described features of certain embodiments of the headend 110, attention is directed to the other portions of the STS 100 shown in FIG. 1. The network 130 may comprise a single network, or a combination of networks (e.g., local and/or wide area networks). Further, the communications medium of the network 130 may comprise a wired connection or wireless connection (e.g., satellite, terrestrial, wireless LAN, etc.), or a combination of both. In the case of wired implementations, the network 130 may comprise a hybrid-fiber coaxial (HFC) medium, coaxial, optical, twisted pair, etc. Other networks are contemplated to be within the scope of the disclosure, including networks that use packets incorporated with and/or are compliant to MPEG-2 transport or other transport layers or protocols.

The DHCT 200 is typically situated at a user's residence or place of business and may be a stand-alone unit or integrated into another device such as, for example, the display device 140, a personal computer, personal digital assistant (PDA), mobile phone, among other devices. In other words, the DHCT 200 (also referred to herein as a digital receiver or processing device or client device) may comprise one of many devices or a combination of devices, such as a set-top box, television with communication capabilities, cellular phone, personal digital assistant (PDA), or other computer or computer-based device or system, such as a laptop, personal computer, DVD/CD recorder, among others. As set forth above, the DHCT 200 may be coupled to the display device 140 (e.g., computer monitor, television set, etc.), or in some embodiments, may comprise an integrated display (with or without an integrated audio component).

The DHCT 200 receives signals (video, audio and/or other data) including, for example, digital video signals in a compressed representation of a digitized video signal such as, for example, AVC streams modulated on a carrier signal, and/or analog information modulated on a carrier signal, among others, from the headend 110 through the network 130, and provides reverse information to the headend 110 through the network 130. As explained further below, the DHCT 200 comprises, among other components, a video decoder and a decoded picture buffer (DPB).

The television services are presented via respective display devices 140, each which typically comprises a television set that, according to its type, is driven with an interlaced scan video signal or a progressive scan video signal. However, the display devices 140 may also be any other device capable of displaying video images including, for example, a computer monitor, a mobile phone, game device, etc. In one implementation, the display device 140 is configured with an audio component (e.g., speakers), whereas in some implementations, audio functionality may be provided by a device that is separate yet communicatively coupled to the display device 140 and/or DHCT 200. Although shown communicating with a display device 140, the DHCT 200 may communicate with other devices that receive, store, and/or process video streams from the DHCT 200, or that provide or transmit video streams or uncompressed video signals to the DHCT 200.

The STS 100 comprises additional components and/or facilities not shown, as should be understood by one having ordinary skill in the art. For instance, the STS 100 may comprise one or more additional servers (Internet Service Provider (ISP) facility servers, private servers, on-demand servers, channel change servers, multi-media messaging servers, program guide servers), modulators (e.g., QAM, QPSK, etc.), routers, bridges, gateways, multiplexers, transmitters, and/or switches (e.g., at the network edge, among other locations) that process and deliver and/or forward (e.g., route) various digital services to subscribers.

In one embodiment, the AI system comprises the headend 110 and one or more of the DHCTs 200. In some embodiments, the AI system comprises portions of each of these components, or in some embodiments, one of these components or a subset thereof. In some embodiments, one or more additional components described above yet not shown in FIG. 1 may be incorporated in an AI system, as should be understood by one having ordinary skill in the art in the context of the present disclosure.

FIG. 2 is an example embodiment of select components of a DHCT 200. It should be understood by one having ordinary skill in the art that the DHCT 200 shown in FIG. 2 is merely illustrative, and should not be construed as implying any limitations upon the scope of the disclosure. In one embodiment, an AI system may comprise all components shown in, or described in association with, the DHCT 200 of FIG. 2. In some embodiments, an AI system may comprise fewer components, such as those limited to facilitating and implementing decoding functionality. In some embodiments, functionality of the AI system may be distributed among the DHCT 200 and one or more additional devices as mentioned above.

The DHCT 200 includes a communication interface 202 (e.g., depending on the implementation, suitable for coupling to the Internet, a coaxial cable network, an HFC network, satellite network, terrestrial network, cellular network, etc.) coupled in one embodiment to a tuner system 204. The tuner system 204 includes one or more tuners for receiving downloaded (or transmitted) media content. The tuner system 204 can select from among a plurality of transmission signals provided by the STS 100 (FIG. 1). The tuner system 204 enables the DHCT 200 to tune to downstream media and data transmissions, thereby allowing a user to receive digital media content via the STS 100. In one embodiment, analog TV signals can be received via the tuner system 204. The tuner system 204 includes, in one implementation, an out-of-band tuner for bi-directional data communication and one or more tuners (in-band) for receiving television signals. In some embodiments (e.g., an IPTV-configured DHCT), the tuner system 204 may be omitted.

The tuner system 204 is coupled to a signal processing system 206 that in one embodiment comprises a transport demultiplexing/parsing system 208 (demux/pars, or hereinafter, demux) and a demodulating system 210 for processing broadcast and/or on-demand media content and/or data. One or more of the components of the signal processing system 206 may be implemented with software, a combination of software and hardware, or in hardware. The demodulating system 210 comprises functionality for demodulating analog or digital transmission signals.

The components of the signal processing system 206 are generally capable of QAM demodulation (though in some embodiments, other modulation formats may be processed such as QPSK, etc.), forward error correction, demultiplexing of MPEG-2 transport streams, and parsing of packets and streams. The signal processing system 206 has capabilities, such as filters, to detect bit patterns corresponding to fields in the transport packet's header information, adaptation field, and/or payload. Stream parsing may include parsing of packetized elementary streams or elementary streams. Packet parsing may include parsing and processing of data fields, such as the data fields in the adaptation fields in the transport packets that deliver assistive information, among other information.

In one embodiment, the parsing is performed by the signal processing system 206 (e.g., demux 208) extracting the assistive information and one or more processors 212 (one shown) processing and interpreting the assistive information. In some embodiments, the processor 212 performs the parsing, processing, and interpretation. The signal processing system 206 further communicates with the processor 212 via interrupt and messaging capabilities of the DHCT 200.

Concurrently, the signal processing system 206 precludes further processing of packets in the multiplexed transport stream that are irrelevant or not desired, such as packets of data corresponding to other video streams. As indicated above, parsing capabilities of the signal processing system 206 allow for the ingesting by the DHCT 200 of program associated information carried in the transport packets. The demux 208 is configured to identify and extract information in the transport stream to facilitate the identification, extraction, and processing of the compressed pictures. Such information includes Program Specific Information (PSI) (e.g., Program Map Table (PMT), Program Association Table (PAT), etc.) and parameters or syntactic elements (e.g., Program Clock Reference (PCR), time stamp information, payload_unit_start_indicator, etc.) of the transport stream (including packetized elementary stream (PES) packet information). For instance, in some embodiments, a flag, field, or other indicator may be provided in the transport stream (e.g., adaptation field of one or more transport packets) that indicates to the decoding logic (or other components of the DHCT 200) that the video stream includes certain information to assist in decoding of concatenated streams.

In general, information extracted by the demux 208 may include information that assists PVR logic embodied in one embodiment as PVR application 214, as explained further below. Note that in some embodiments, the PVR application 214 may opt to disregard or modify the received information. In some embodiments, portions of the information may not be transmitted for defined periods of time of a program, or for portions of a video stream, such as portions corresponding to a commercial.

In an alternate embodiment, assistive information is extracted from the video stream and processed by decompression engine 218. In yet another embodiment, assistive information is extracted from the video stream and processed by processor 212. And in yet another embodiment, assistive information is extracted from the video stream by decompression engine 218 and interpreted by processor 212.

In one embodiment, the demux 208 is configured with programmable hardware (e.g., PES packet filters). In some embodiments, the signal processing system 206 or one or more components thereof is configured in software, hardware, or a combination of hardware and software.

The signal processing system 206 is coupled to one or more busses (a single bus 216 is shown) and to decoding logic configured in one embodiment as a decompression engine 218 (or media engine). In some embodiments, reference to decoding logic may include one or more additional components, such as memory, processor 212, etc. The decompression engine 218 comprises a video decompression engine 220 (or video decoder or video decompression logic) and audio decompression engine 222 (or audio decoder or audio decompression logic). The decompression engine 218 is further coupled to decompression engine memory 224 (or media memory or memory), the latter which, in one embodiment, comprises one or more respective buffers for temporarily storing compressed (compressed picture buffer or bit buffer, not shown) and/or reconstructed pictures (decoded picture buffer or DPB). In some embodiments, one or more of the buffers of the decompression engine memory 224 may reside in whole or in part in other or additional memory (e.g., memory 226) or components.

The DHCT 200 further comprises additional components coupled to the bus 216. For instance, the DHCT 200 further comprises a receiver 228 (e.g., infrared (IR), radio frequency (RF), etc.) configured to receive user input (e.g., via direct-physical or wireless connection via a keyboard, remote control, voice activation, etc.) to convey a user's request or command (e.g., for program selection, stream manipulation such as fast forward, rewind, pause, channel change, etc.), the processor 212 (indicated above) for controlling operations of the DHCT 200, and a clock circuit 230 comprising phase and/or frequency locked-loop circuitry to lock into a system time clock (STC) from a program clock reference, or PCR, received in the video stream to facilitate decoding and output operations.

For instance, time stamp information (e.g., presentation time stamp/decode time stamp, or PTS/DTS) in the received video stream is compared to the reconstructed system time clock (STC) (generated by the clock circuit 230) to enable a determination of when the buffered compressed pictures are provided to the video decompression engine 220 for decoding (DTS) and when the buffered, decoded pictures are output by the video decompression engine 220 according to their PTS via the output system 254. The output system 254 hence may comprise graphics and display pipelines and output logic including HDMI, DENC, or other known systems. In some embodiments, the clock circuit 230 may comprise plural (e.g., independent or dependent) circuits for respective video and audio decoding operations and output processing operations. Although described in the context of hardware circuitry, some embodiments of the clock circuit 230 may be configured as software (e.g., virtual clocks) or a combination of hardware and software.

The DHCT 200 further comprises memory 226, which comprises volatile and/or non-volatile memory, and is configured to store executable instructions or code associated with an operating system (O/S) 232, one or more other applications 234 (e.g., the PVR application 214, interactive programming guide (IPG), video-on-demand (VOD), WatchTV (associated with broadcast network TV), among other applications not shown such as pay-per-view, music, etc.), and driver software 236.

The DHCT 200 further comprises one or more storage devices (one shown, storage device 238). The storage device 238 may be located internal to the DHCT 200 and coupled to the bus 216 through a communication interface 250. The communication interface 250 may include an integrated drive electronics (IDE), small computer system interface (SCSI), IEEE-1394 or universal serial bus (USB), among others. In one embodiment, the storage device 238 comprises associated control logic, such as a controller 240, that in coordination with one or more associated drivers 236 effects the temporary storage of buffered media content and/or more permanent storage of recorded media content. Herein, references to write and/or read operations to the storage device 238 is understood to refer to write and/or read operations to/from one or more storage mediums of the storage device 238.

The device driver 236 is generally a software module interfaced with and/or residing in the operating system 232. The device driver 236, under management of the operating system 232, communicates with the storage device controller 240 to provide the operating instructions for the storage device 238. As conventional device drivers and device controllers are well known to those of ordinary skill in the art, further discussion of the detailed working of each will not be described further here. The storage device 238 may further comprise one or more storage mediums 242 such as hard disk, optical disk, or other types of mediums, and an index table 244, among other components (e.g., FAT, program information, etc.) as should be understood by one having ordinary skill in the art. In some embodiments, the storage device 238 may be configured as non-volatile memory or other permanent memory.

In one implementation, video streams are received in the DHCT 200 via communications interface 202 and stored in a temporary memory cache (not shown). The temporary memory cache may be a designated section of memory 226 or an independent memory attached directly, or as part of a component in the DHCT 200. The temporary cache is implemented and managed to enable media content transfers to the storage device 238 (e.g., the processor 212 causes the transport stream in memory 226 to be transferred to a storage device 238). In some implementations, the fast access time and high data transfer rate characteristics of the storage device 238 enable media content to be read from the temporary cache and written to the storage device 238 in a sufficiently fast manner. Multiple simultaneous data transfer operations may be implemented so that while data is being transferred from the temporary cache to the storage device 238, additional data may be received and stored in the temporary cache.

Alternatively or additionally, the storage device 238 may be externally connected to the DHCT 200 via a communication port, such as communication port 252. The communication port 252 may be configured according to IEEE-1394, USB, SCSI, or IDE, among others. The communications port 252 (or ports) may be configured for other purposes, such as for receiving information from and/or transmitting information to devices other than an externally-coupled storage device.

One having ordinary skill in the art should understand that the DHCT 200 may include other components not shown, including compression engine, decryptors, samplers, digitizers (e.g., analog-to-digital converters), multiplexers, conditional access processor and/or application software, Internet browser, among others. In some embodiments, functionality for one or more of the components illustrated in, or described in association with, FIG. 2 may be combined with another component into a single integrated component or device or distributed among several components or devices.

The AI system may comprise the entirety of the DHCT 200 in one embodiment, the headend 110 in some embodiments, or a combination of both components in certain embodiments. In some embodiments, the AI system may comprise or one or more components or sub-components thereof, or additional components not shown. The AI system (including in some embodiments the splicer 112 (or portions thereof), the encoder 111 (or portions thereof), and/or the DHCT 200 (or portions thereof)), may be implemented in hardware, software, firmware, or a combination thereof. To the extent certain embodiments of the AI system or a portion thereof are implemented in software or firmware, executable instructions for performing one or more tasks of the AI system are stored in memory or any other suitable computer readable medium and executed by a suitable instruction execution system. In the context of this document, a computer readable medium is an electronic, magnetic, optical, or other physical device or means that can contain or store a computer program for use by or in connection with a computer related system or method.

To the extent certain embodiments of the AI system or portions thereof are implemented in hardware, the AI system may be implemented with any or a combination of the following technologies, which are all well known in the art: a discrete logic circuit(s) having logic gates for implementing logic functions upon data signals, an application specific integrated circuit (ASIC) having appropriate combinational logic gates, programmable hardware such as a programmable gate array(s) (PGA), a field programmable gate array (FPGA), etc.

Having described an example environment and corresponding components of certain embodiments of AI systems, attention is directed to FIGS. 3A and 3B, which respectively provides an illustration of the provision (and absence thereof) of assistive information pertaining to DPB properties. FIG. 3A shows a network feed 302 in decode order and in output order 304. The network feed 302 comprises three consecutive, equal-length segments 306, 308, and 310, and the output order version similarly comprises three consecutive, equal length segments 312, 314, and 316. The decode order stream 304 further illustrates network out-point (splice-out point) 305 and network in-point (splice-in point) 307 corresponding to the spliced-in second or tail stream 314. In other words, for the output order version 304, segments 312 and 316 each comprise a portion of a head stream, and segment 314 comprises a tail stream spliced into the head stream between segments 312 and 316. Based on assistive information conveyed in the associated transport stream (e.g., as described above), the YTBOP of the DPB associated with the head stream is incorporated into each splice point 305 and 307 to provide a graceful transition between concatenations. In other words, each splice point 305 and 307 corresponds respectively to YTBOP 318 and 320 of a DPB. The spliced in-point 307 requires the following buffering: (PTS_(in-1)−DTS_(in-i))=YTBOP+1, where YTBOP is the number of yet to be output pictures in the head stream 312 at the splice-out point, PTS_(in-1) is the first output picture in the tail stream 314, and DTS_(in-1) is the first DTS in the tail stream 314. For purposes of illustration, each YTBOP comprises six pictures representing 25% of the frame rate (e.g., for each splice point, representing approximately 0.25 seconds).

FIG. 3B similarly comprises an example where the YTBOP interval described above is not honored, and in particular, illustrating the need for the in-point to abide by (PTS_(in-1)−DTS_(in-i))=YTBOP+1. In particular, a decode order stream 322 and output order version 324 each comprise plural consecutive segments (326, 328, 330 for the decode order 322 and 332, 336, and 338 for the output order 324). As shown, without the YTBOP interval at the splice-out point 309, the tail stream 336 is spliced in, using the example parameters above, 0.25 seconds too early. Such a result may occur due to a no_output_of_prior_pics_flag equal to one (1). As expressed above, with gaps in output time (e.g., non-contiguous PTS) of pictures in the DPB yet to be output at the splice point, a compliant AVC decoder is challenged—the no_output_of_prior_pics_flag is set equal to one (1) to prevent the output of those YTBOP pictures in the DPB. If the output of these decoded pictures is skipped (e.g., not displayed), a splicing device needs to improvise to for a number of output intervals equal to the number of DPB pictures that are not output (e.g., per a YTBOP flag) while accumulating pictures into the CPB to raise buffer levels (e.g., to avoid buffer underflow). With multiple splice operations, as noted above, the skipping of decoded pictures raises the risk of buffer underflow. If the latest PTS among the pictures yet to be output in the DPB at the splice point is signaled (e.g., last_PTS_flag), then a splicing device, without having to decode and determine based on the decoding operation, knows to provide that many pictures (delay their output) to compensate for the non-output, decoded pictures. While filling the CPB, a receiver either has to blank out pictures (e.g., black pictures, such as the 0.50 second interval shown in FIG. 3B) or continuously repeat the last output picture prior to the splice point. One mechanism to achieve this function is by the splicing device signaling the last output picture to be repeated. Further, byte stuffing in blank pictures may raise the CPB buffer level. Accordingly, the assistive information pertaining to the DPB properties includes, in one embodiment, the configuring of the YTBOP of the head stream (at the out-point) with a maximum of sixteen 16 (e.g., four (4) bits), and a YTBOP_flag that provides all YTBOP pictures in the DPB have successive picture-output times and the first output time of the YTBOP pictures is the first frame interval after the out-point.

The YTBOP intervals at each splice point allow for an overlap transition period over YTBOP frame intervals, enabling a graceful output transition and/or better bit-rate management. In other words, the inclusion of the YTBOP intervals enables the splicer 112 to perform better stream conditioning, where pictures from the headstream are output from the DPB while pictures from the tail stream are being decoded and stored in the DPB, while avoiding error in CPB buffer management.

In some embodiments, as expressed above, optional assistive information may be provided to the DHCT 200 when there are YTBOPs in the DPB having discontinuous output times, for instance in non-seamless applications. For instance, one example embodiment of “yet to be output pictures” (YTBOP) message syntax is as follows:

C Descriptor pic_output_cue( payloadSize ) { num_prior_pics_in_dpb 5 u(5) for (j = 0; j < num_prior_pics_in_dpb; j++) { output_cue[ i ] 5 u(3)  }

This example message assists the DHCT 200 in outputting prior pictures remaining in DPB from the head stream. The message helps a decoder in the DHCT 200 to maintain continuous picture output for streams having YTBOPs with discontinuous output times. The YTBOP message semantics are described below as follows:

num_prior_pics_in_dpb indicates the number of YTBOP remaining in the DPB at the splice out-point. output_cue[i] indicates cues for the output of each respective YTBOP in the DPB, according to the Table below. The pictures are sorted by corresponding picture order counts from smallest value to highest value.

Value Recommended output cue for picture 0 Picture may be discarded without output 1 Picture may be output according to picture's pic_struct* 2 Picture's output as indicated by pic_struct* may be repeated once 3 Picture's output as indicated by pic_struct* may be repeated twice 4 Picture's output as indicated by pic_struct* may be repeated indefinitely until first picture is output from DPB after the decoding of the IDR access unit 5 . . . 7 Reserved *For interlaced video source, repetition means that the last output field of an interlaced frame is output as both the top and bottom fields to satisfy the number of repetitions specified by output cue.

In some embodiments, assistive information messaging is provided that assists decoding logic of the DHCT 200 in processing YTBOPs of the DPB where discontinuities or gaps arise from no_output_of_prior_pics_flags with a value of one (1) alone or in association with an IDR access unit. For instance, when a compliant (e.g., compliant to MPEG-2) DHCT receives a no_output_of_prior_pics_flag=1, the compliant DHCT outputs a blank picture or frozen frame intervals. One alternative approach to handling such a stream parameter is to selectively control the output of each otherwise discarded DPB picture at the splice-out point. One example embodiment of assistive information configured as a picture output message syntax is as follows:

C Descriptor pic_output( payloadSize ) { num_prior_pics_in_dpb 5 u(5) for (j = 0; j < num_prior_pics_in_dpb; j++) { output_cue[ i ] 5 u(3)  } This example message applies to the control and management of YTBOPs from the DPB at splice out-points. The pictures output message semantics are described below as follows: num_prior_pics_in_dpb indicates the number of YTBOPs in the DPB at a corresponding splice out-point. This may be accompanied by an IDR access unit and issuance of the no_output_of_prior_Pics_flag in AVC video with a value of 1. output_cue[i] indicates cues for the output of each prior picture in the DPB, according to the following Table. The pictures are sorted by corresponding picture order counts from smallest value to highest value. The decoder may make use of the output_cue for better visual experience.

Value Recommended output cue for picture 0 Picture may be discarded without output 1 Picture may be output according to picture's pic_struct* 2 Picture's output as indicated by pic_struct* may be repeated once 3 Picture's output as indicated by pic_struct* may be repeated twice 4 Picture's output as indicated by pic_struct* may be repeated indefinitely until first picture is output from DPB after the decoding of the IDR access unit 5 Repeat picture output as indicated by pic_struct* until the output time of the next picture in the DPB. 6 Output the last picture once again* 7 Reserved *For interlaced video source, repetition means that the last output field of an interlaced frame is output as both the top and bottom fields to satisfy the number of repetitions specified by output cue.

Through the use of the assistive information provided via these or other suitable message syntaxes, pictures may be output from the DPB in a manner that reduces output discontinuities and gaps at non-seamless concatenations. For instance, rather than outputting a last picture of the DPB repeatedly at a concatenation when no_output_of_prior_pics_flag is equal to one (1) (due to non-contiguous output times or gaps), the assistive information comprises a mechanism to issue a control command for each YTBOP in the DPB such that some pictures are repeated and/or some pictures are displayed only once.

It is noted that in some embodiments, the second field of an interlaced frame may be repeated just once. For instance, for a top-field-first frame, one display order is as follows: top-field (at top-field position), bottom-field (at bottom-field position), bottom-field (at top-field position). One benefit of such a scheme, among others, is that of assisting the display process of the DHCT 200 in case of a splice that leads to a field parity violation at the splice point. In other words, sometimes for a transition in field parity at a splice, there is a need for an odd number of fields (by repetition of the last field of an interlaced frame), and with the last field position on the lines of the opposite parity (e.g., the lines of an odd field displayed on the even lines).

In view of the above description, it should be appreciated that one AI method embodiment 400, implemented by the headend 110 and shown in FIG. 4, comprises providing a transport stream to a splicing device, the transport stream comprising a head stream concatenated to a tail stream, the head stream and the tail stream each comprising a compressed video sequence from a separate video source (402); providing in an adaptation field of a transport stream packet corresponding to the head stream an out-point that corresponds to a provided splice point, the splice point provided based on presentation time stamp (PTS) value, the out-point signaled by a descriptor in a program map table (PMT), the transport packet further comprising assistive information comprising one or more compressed picture buffer (CPB) properties and one or more decoded picture buffer (DPB) properties that are used in the concatenation of the head stream and the tail stream (404).

In view of the above description, it should be appreciated that another AI method embodiment 500, as shown in FIG. 5 and implemented by a splicer 112, comprises receiving a transport stream, the transport stream comprising a head stream concatenated to a tail stream, the head stream and the tail stream each comprising a compressed video sequence from a separate video source (502); and receiving in an adaptation field of a transport stream packet corresponding to the head stream an out-point that corresponds to a provided splice point, the splice point provided based on presentation time stamp (PTS) value, the out-point signaled by a descriptor in a program map table (PMT), the transport packet further comprising assistive information comprising one or more compressed picture buffer (CPB) properties and one or more decoded picture buffer (DPB) properties that are used in the concatenation of the head stream and the tail stream (504).

Note that the methods described in FIGS. 4-5 may also be implemented in other components or systems, in whole or in part, such as at a client device, hub, etc.

Any process descriptions or blocks in flow charts or flow diagrams should be understood as representing modules, segments, or portions of code which include one or more executable instructions for implementing specific logical functions or steps in the process, and alternate implementations are included within the scope of the present disclosure in which functions may be executed out of order from that shown or discussed, including substantially concurrently or in reverse order, depending on the functionality involved, as would be understood by those reasonably skilled in the art. In some embodiments, steps of a process identified in FIGS. 4-5 using separate boxes can be combined. Further, the various steps in the flow diagrams illustrated in conjunction with the present disclosure are not limited to the architectures described above in association with the description for the flow diagram (as implemented in or by a particular module or logic) nor are the steps limited to the example embodiments described in the specification and associated with the figures of the present disclosure. In some embodiments, one or more steps may be added to one or more of the methods described in FIGS. 4-5, either in the beginning, end, and/or as intervening steps, and that in some embodiments, fewer steps may be implemented.

It should be emphasized that the above-described embodiments of the disclosure are merely possible examples, among others, of the implementations, setting forth a clear understanding of the principles of the disclosure. Many variations and modifications may be made to the above-described embodiments without departing substantially from the principles set forth herein. All such modifications and variations are intended to be included herein within the scope of the disclosure. In addition, the scope of the disclosure includes embodying the functionality of the embodiments in logic embodied in hardware and/or software-configured mediums. 

1. A method, comprising: receiving a transport stream comprising a head stream and a tail stream, the head stream and the tail stream each comprising a compressed video sequence from a separate video source; processing an adaptation field of a transport packet corresponding to the head stream, the adaptation field comprising a splice out-point that corresponds to a splice point, the splice point provided based on a presentation time stamp value, the splice out-point signaled by a descriptor in a program map table, the transport packet further comprising assistive information comprising one or more compressed picture buffer properties and one or more decoded picture buffer properties; and concatenating the head stream and the tail stream based on the compressed picture buffer properties and the decoded picture buffer properties, wherein the compressed picture buffer properties comprise at least a coding level, and wherein the decoded picture buffer properties comprise a first flag corresponding to a presentation time stamp value corresponding to a last picture in the decoded picture buffer, and wherein the decoded picture buffer properties further comprise a second flag, the second flag signaling that all pictures yet to be output residing in the decoded picture buffer have successive picture output times, wherein the second flag further signals a first output time of the pictures yet to be output, wherein the first output time corresponds to a first frame interval after the splice out-point.
 2. The method of claim 1, wherein the provided splice point is received according to a message compliant with Society of Cable and Telecommunications Engineers Standard 35—Digital Program Insertion Cueing Message for Cable.
 3. The method of claim 1, wherein the transport packet is located immediately prior to the splice out-point connecting the head stream to the tail stream.
 4. The method of claim 1, wherein the descriptor comprises an elementary stream descriptor loop of the program map table.
 5. The method of claim 1, wherein the coding level comprises an Advanced Video Coding level.
 6. The method of claim 1, wherein the compressed picture buffer properties further comprise a value corresponding to a decoded time stamp value minus a system time clock value.
 7. The method of claim 1, wherein the compressed picture buffer properties further comprise a value corresponding to a decoded time stamp value minus a system time clock value and a buffer level.
 8. The method of claim 1, wherein the compressed picture buffer properties further comprise a value corresponding to a decoded time stamp value minus a system time clock value, a buffer level, and an intended compressed picture buffer upper bound level and compressed picture buffer lower bound level.
 9. The method of claim 1, further comprising honoring a yet to be output picture interval at the splice out-point and a splice in-point, the splice in-point corresponding to the splice in point connecting the tail stream to the head stream.
 10. The method of claim 1, wherein responsive to a no_output_of_prior_pics_flag_value equal to one (1), outputting pictures equal to a value corresponding to a last_PTS flag provided in the assistive information while filling a compressed picture buffer.
 11. The method of claim 10, wherein outputting the pictures comprises repeating a last picture output prior to the splice out-point.
 12. The method of claim 10, wherein outputting the pictures comprises repeating the output of blank pictures.
 13. A digital home communications terminal, comprising: a processor configured to: receive an adaptation field of a transport stream packet corresponding to a head stream a splice out-point that corresponds to a provided splice point, the splice point provided based on a presentation time stamp value, the splice out-point signaled by a descriptor in a program map table; receive a compressed picture buffer property corresponding to a coding level of the transport stream packet; and receive decoded picture buffer properties comprising a first flag corresponding to a last presentation time stamp value corresponding to a last picture in the decoded picture buffer, and a second flag signaling that all of the plurality of pictures yet to be output residing in the decoded picture buffer have successive picture output times.
 14. The digital home communications terminal of claim 13, wherein the head stream is concatenated to a tail stream, the head stream and the tail stream each comprising a compressed video sequence from a separate video source.
 15. The digital home communications terminal of claim 14, the processor further configured to honor a yet to be output picture interval at the splice out-point and a splice in-point, the splice in-point corresponding to the splice in point connecting the tail stream to the head stream.
 16. The digital home communications terminal of claim 14, the processor further configured to output pictures equal to a value corresponding to a last_PTS flag provided in the assistive information while filling a compressed picture buffer responsive to a no_output_of_prior_pics_flag_value equal to one (1).
 17. The digital home communications terminal of claim 14, the processor further configured to, wherein outputting the pictures comprises repeating a last picture output prior to the splice out-point.
 18. The digital home communications terminal of claim 13, wherein the compressed picture buffer properties further comprises one or more of a value corresponding to a decoded time stamp value minus a system time clock value, a buffer level, and an intended compressed picture buffer upper bound level and compressed picture buffer lower bound level.
 19. The digital home communications terminal of claim 13, wherein the decoded picture buffer properties comprises a first flag corresponding to a last presentation time stamp value corresponding to a last picture in the decoded picture buffer and a second flag, the second flag signaling that all of the plurality of pictures yet to be output residing in the decoded picture buffer have successive picture output times.
 20. A client device, comprising: a processor configured to: receive a transport stream comprising a head stream and a tail stream, the head stream and the tail stream each comprising a compressed video sequence from a separate video source; and process an adaptation field of a transport packet corresponding to the head stream a splice out-point that corresponds to a splice point, the splice point provided based on a presentation time stamp value, the splice out-point signaled by a descriptor in a program map table, the transport packet further comprising assistive information comprising one or more compressed picture buffer properties and one or more decoded picture buffer properties; and concatenate the head stream and the tail stream based on the compressed picture buffer properties and the decoded picture buffer properties, wherein the compressed picture buffer properties comprise at least a coding level, and wherein the decoded picture buffer properties comprise a first flag corresponding to a presentation time stamp value corresponding to a last picture in the decoded picture buffer, and wherein the decoded picture buffer properties further comprise a second flag, the second flag signaling that all pictures yet to be output residing in the decoded picture buffer have successive picture output times, wherein the second flag further signals a first output time of the pictures yet to be output, wherein the first output time corresponds to a first frame interval after the splice out-point. 